Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29a51ee551078ce3c73f44313bae9812aa7ba51da936a4cd4906da04255b06be

Tx prefix hash: 7ef9cc0cadb2b2e03ec914cd24234d443f1c986dbefd763305c8d4652270471e
Tx public key: 30959ee8786f165568f4ed80bad26a3e44a49e5a0c23a619a7a383cf0de9b8af
Timestamp: 1661469712 Timestamp [UCT]: 2022-08-25 23:21:52 Age [y:d:h:m:s]: 02:216:00:54:19
Block: 573838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 675635 RingCT/type: yes/0
Extra: 0130959ee8786f165568f4ed80bad26a3e44a49e5a0c23a619a7a383cf0de9b8af021100000010e6d27f9c000000000000000000

1 output(s) for total of 7.702586637000 dcy

stealth address amount amount idx
00: 2b62bc9a2f0cb118264a83416a5f5d9b176f03cc43a997b958da9e68584fea5a 7.702586637000 1007136 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": 573848, "vin": [ { "gen": { "height": 573838 } } ], "vout": [ { "amount": 7702586637, "target": { "key": "2b62bc9a2f0cb118264a83416a5f5d9b176f03cc43a997b958da9e68584fea5a" } } ], "extra": [ 1, 48, 149, 158, 232, 120, 111, 22, 85, 104, 244, 237, 128, 186, 210, 106, 62, 68, 164, 158, 90, 12, 35, 166, 25, 167, 163, 131, 207, 13, 233, 184, 175, 2, 17, 0, 0, 0, 16, 230, 210, 127, 156, 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