Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb4d7b4cd0f6b0fbea65a8977577e1da1fbeb63b03c406a489dd94f1fde85618

Tx prefix hash: ea98e1e5bcc14a0fbac727dc183ad2d9f8ea1adbbbc00010d12eb25929b8ef17
Tx public key: 9bbfeb43e501d2e922e336d77ac812c05b0da8d4927bd8f01d83279eb181f841
Timestamp: 1695962334 Timestamp [UCT]: 2023-09-29 04:38:54 Age [y:d:h:m:s]: 01:105:14:03:35
Block: 858479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336727 RingCT/type: yes/0
Extra: 019bbfeb43e501d2e922e336d77ac812c05b0da8d4927bd8f01d83279eb181f841021100000008faf35c9c000000000000000000

1 output(s) for total of 0.878016638000 dcy

stealth address amount amount idx
00: fe7403a51cf970f9c4237cba611b3ed4804d2e441a7fe3c5414931a359c0714e 0.878016638000 1312655 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": 858489, "vin": [ { "gen": { "height": 858479 } } ], "vout": [ { "amount": 878016638, "target": { "key": "fe7403a51cf970f9c4237cba611b3ed4804d2e441a7fe3c5414931a359c0714e" } } ], "extra": [ 1, 155, 191, 235, 67, 229, 1, 210, 233, 34, 227, 54, 215, 122, 200, 18, 192, 91, 13, 168, 212, 146, 123, 216, 240, 29, 131, 39, 158, 177, 129, 248, 65, 2, 17, 0, 0, 0, 8, 250, 243, 92, 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