Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e67cf2a8382b2aa175bfe3be195d215abc37432681e779ff3a0ac602311d31

Tx prefix hash: d0c31162a0a5fc8ac3a0f936f3034efe4e41bda51c6e5ad9677d45279c99239e
Tx public key: f9a21d04ae869b4930aee0ce76db6aaf58dbaf3ec1f279378a62129858f948f7
Timestamp: 1674156707 Timestamp [UCT]: 2023-01-19 19:31:47 Age [y:d:h:m:s]: 02:146:11:04:44
Block: 678353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 626308 RingCT/type: yes/0
Extra: 01f9a21d04ae869b4930aee0ce76db6aaf58dbaf3ec1f279378a62129858f948f702110000000152542ceb000000000000000000

1 output(s) for total of 3.470043014000 dcy

stealth address amount amount idx
00: 9dcfc01415aae426fa8dbf4378dc23206f3df7134e5e46ca1b67bf7a6071301b 3.470043014000 1120226 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": 678363, "vin": [ { "gen": { "height": 678353 } } ], "vout": [ { "amount": 3470043014, "target": { "key": "9dcfc01415aae426fa8dbf4378dc23206f3df7134e5e46ca1b67bf7a6071301b" } } ], "extra": [ 1, 249, 162, 29, 4, 174, 134, 155, 73, 48, 174, 224, 206, 118, 219, 106, 175, 88, 219, 175, 62, 193, 242, 121, 55, 138, 98, 18, 152, 88, 249, 72, 247, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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