Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 233131ffdf02431a58006eb8f236d9035ebe494a859e1afd4569d723d1f29e6c

Tx prefix hash: 3539d33dd87f7088d6009c4d1aeae850c48ae12eecbed6534f822b1b86e774ee
Tx public key: a76f88548b77d2e2ef5b12a102051775c8beff10df1c60fa5218c33649d8afdb
Timestamp: 1722967094 Timestamp [UCT]: 2024-08-06 17:58:14 Age [y:d:h:m:s]: 01:091:06:41:21
Block: 1082148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323702 RingCT/type: yes/0
Extra: 01a76f88548b77d2e2ef5b12a102051775c8beff10df1c60fa5218c33649d8afdb02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50e5963b65a01f45628d05c7f2c7c3ee6ea52b2039a83f2b9d16a15110f6d420 0.600000000000 1555971 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1082158, "vin": [ { "gen": { "height": 1082148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50e5963b65a01f45628d05c7f2c7c3ee6ea52b2039a83f2b9d16a15110f6d420" } } ], "extra": [ 1, 167, 111, 136, 84, 139, 119, 210, 226, 239, 91, 18, 161, 2, 5, 23, 117, 200, 190, 255, 16, 223, 28, 96, 250, 82, 24, 195, 54, 73, 216, 175, 219, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8