Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bff8d148f9849bf5646603dc2885081f1610dbccf8df2035241c0fb52e0f74fb

Tx prefix hash: a7eb5158049a9570d881850f1d15a69f122a7a31f78be4c3255cb91ef54e7b16
Tx public key: 499a72c1b12a146297f5de304f4112e9f4c5b1ef49e6a63fd951337ff0f7319a
Timestamp: 1673958551 Timestamp [UCT]: 2023-01-17 12:29:11 Age [y:d:h:m:s]: 02:080:13:15:56
Block: 676709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579226 RingCT/type: yes/0
Extra: 01499a72c1b12a146297f5de304f4112e9f4c5b1ef49e6a63fd951337ff0f7319a02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.513841074000 dcy

stealth address amount amount idx
00: 40b0a04a41b32d6b0de1dcffd34a6e4b3e2cca38fb1aa5ea8a0021d80a7e3ce5 3.513841074000 1118434 of 0

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": 676719, "vin": [ { "gen": { "height": 676709 } } ], "vout": [ { "amount": 3513841074, "target": { "key": "40b0a04a41b32d6b0de1dcffd34a6e4b3e2cca38fb1aa5ea8a0021d80a7e3ce5" } } ], "extra": [ 1, 73, 154, 114, 193, 177, 42, 20, 98, 151, 245, 222, 48, 79, 65, 18, 233, 244, 197, 177, 239, 73, 230, 166, 63, 217, 81, 51, 127, 240, 247, 49, 154, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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