Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e47f1a17854d5a138596df2092cb69c51703095d7cf4ebf4dff5b79cbd9e772

Tx prefix hash: cc5fbee869a088f372c37483f1c109ccb6608a2c1fbdb16dd5fa46951f596c43
Tx public key: 867b9a6ba63fa10f21084b4b474997497b431820a7bc8b1ac1cdb307839b030f
Timestamp: 1673103139 Timestamp [UCT]: 2023-01-07 14:52:19 Age [y:d:h:m:s]: 01:332:11:49:47
Block: 669614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498655 RingCT/type: yes/0
Extra: 01867b9a6ba63fa10f21084b4b474997497b431820a7bc8b1ac1cdb307839b030f02110000000233af99f4000000000000000000

1 output(s) for total of 3.709290146000 dcy

stealth address amount amount idx
00: 352065907825b3e3b7bee19420a5e70ff1fba3ea6d7f6da716dbc6cd31b4dba5 3.709290146000 1110959 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": 669624, "vin": [ { "gen": { "height": 669614 } } ], "vout": [ { "amount": 3709290146, "target": { "key": "352065907825b3e3b7bee19420a5e70ff1fba3ea6d7f6da716dbc6cd31b4dba5" } } ], "extra": [ 1, 134, 123, 154, 107, 166, 63, 161, 15, 33, 8, 75, 75, 71, 73, 151, 73, 123, 67, 24, 32, 167, 188, 139, 26, 193, 205, 179, 7, 131, 155, 3, 15, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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