Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f5a56e00fff6d066aa8971510708047cdd88da6d10f909714911d0846c71902

Tx prefix hash: 8b25f083b8ec8a8832c2f9df1cf6b2cd68c79bfe6950249046441fbcb94492d4
Tx public key: cf2be61a901fe845d95198110b5a33f165548c37e5e5eb76d7a050ae784b2f4e
Timestamp: 1660711587 Timestamp [UCT]: 2022-08-17 04:46:27 Age [y:d:h:m:s]: 03:109:02:07:51
Block: 567586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 857799 RingCT/type: yes/0
Extra: 01cf2be61a901fe845d95198110b5a33f165548c37e5e5eb76d7a050ae784b2f4e021100000008faf35c9c000000000000000000

1 output(s) for total of 8.078897021000 dcy

stealth address amount amount idx
00: 5ad1ed33c6e785840a1fa0fcf4b8dbaeeb31b55e524c6285bd31483eed6a04da 8.078897021000 1000687 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": 567596, "vin": [ { "gen": { "height": 567586 } } ], "vout": [ { "amount": 8078897021, "target": { "key": "5ad1ed33c6e785840a1fa0fcf4b8dbaeeb31b55e524c6285bd31483eed6a04da" } } ], "extra": [ 1, 207, 43, 230, 26, 144, 31, 232, 69, 217, 81, 152, 17, 11, 90, 51, 241, 101, 84, 140, 55, 229, 229, 235, 118, 215, 160, 80, 174, 120, 75, 47, 78, 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